Overall EDM Server performance has improved approximately 20% from optimized security validation. The actual improvement for a particular environment will depend on many variable factors.

New command-line arguments OFFLINEMODE and WEBSERVICESMODE have been added to the client installation packages to make it easier to deploy the Meridian Web Client with local workspace synchronization (Application Integration) set to Remote mode. The default mode for interactive installation when the PowerUser client component is not selected has been changed to Remote mode. The corresponding client registry values OfflineMode, WebServicesMode, and DisableOfflineSwitch in the HKEY_LOCAL_MACHINE hive can now be set for all users of the same PC. They can be overridden for the current user by the values with same names in the HKEY_CURRENT_USER hive.

Microsoft SQL Server 2016 (and SP1) are now supported. SQL Server 2008 is no longer supported.

Resolves a problem with transaction sorting during vault imports.

The Meridian Explorer synchronization engine has been re-engineered to improve performance. The result is 5X-10X faster synchronization depending on the quantities of documents, revisions, tags, references, and projects. Synchronization to MS SQL Server is approximately 10% faster than to Oracle.

Synchronization now includes the document metadata only and the document content can be scheduled to be updated separately.

The method used to synchronize repositories can be selected with a new Synchronization option. An overview of the synchronization jobs for reach repository is now shown on a new Synchronization page of the repository definition where the jobs can be run manually.

By default, Meridian Explorer will show document content that resides in the Meridian Enterprise vault. A new option Document Content has been added to repository definitions. It can be set to import the document content from the source vault to the repository database. New options for the import batch size, multi-threading, and error reporting can be configured to tune the task. It can be run manually or scheduled to run automatically at a desired interval. The copied content can be manually purged from the database with a new command Remove Content, if necessary.

The RENDERING option pages are no longer available for Synchronization type jobs. They are still available for Publish type jobs.

The new synchronization engine requires the Oracle Data Provider for .NET (ODP.NET) x64 version 11.2 or higher be installed on the Meridian Enterprise Server computer in addition to the previous requirement of the Oracle Data Access Components (ODAC).

For more information about how the new synchronization engine affects your existing jobs, see Migrating existing synchronization jobs.

Detection of variant data types in API calls has been improved.

A new server registry key VerboseEventFlags has been added that can be used to enable or disable specific types of extended messages in the event log.

The stability of importing large numbers of documents into Oracle vaults has been improved.

Undeleting and purging of documents and folders are now added to the audit log.

A new option Show mapped users first has been added to the GROUP MAPPINGS list in the Meridian Enterprise Server Administration Console. When enabled, it sorts the list on the AD GROUP column and shows the already mapped groups at the top of the list.

The audit log entry made when a document in a workflow is revoked now includes the document name.

User names shown in the status bar in PowerUser and in the Meridian Web Client are now affected by the UserNameFormat registry setting on the server.

Reconnection to SQL Server after a network failure and error reporting have been improved.

The stability of HyperCache when loading very large vaults has been improved.

The site cache server has been re-engineered for easier deployment, expanded functionality, and better performance:

• It supports both the Meridian Web Client (source documents and renditions) and Meridian Explorer (renditions only).
• It is installed with Meridian Enterprise Server by default and can be installed stand-alone at remote sites.
• Site cache servers (local or remote) may now be registered in the Meridian Enterprise Server Administration Console and configured using a web application running on the site cache server.
• The location of a site cache server for use by a PC is now requested during client software installation and can be set manually in a new setting Site cache URL in the local workspace options of Application Integration. Document transfers will be through the site cache when the new setting Use site cache is enabled in the user’s preferences. This URL saved in the BCSiteCacheURL value of the Windows registry in HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client. It can be overridden for the current user by the same setting in HKEY_CURRENT_USER\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings.
• The site cache is used automatically by a client PC if the Application Integration component is installed on the PC and its site cache settings are configured. A new background process named BlueCieloECM.SiteChache.LwsClient.exe runs on the client PC.
• If a site cache is enabled for a client PC and the Enable Web Access client components option is also enabled, the client component (ActiveX) is used only for BlueCielo viewer (if enabled), importing documents (instead of the HTML component), and running workflow transitions on multiple documents.
• Site cache servers now forward client requests for documents that reside on Meridian EDM servers that are on the same network segment as the site cache server directly to the EDM server to prevent unnecessary caching.
• The site cache server now supports Windows authentication.
• Site caches now support shared workspaces in Offline mode.
• Deleted master documents and revoked revisions are removed from the local workspaces.

A new registry setting UsePDFTron has been added to Web Access that, when set to 1, forces all renditions in the Meridian Web Client to be shown in PDFTron.

The average performance of the EDM Server has been improved approximately 13% over 2016 SP1 and the performance during long periods of heavy loads is more consistent.

The Delete manual reference event no longer generates two entries in the audit log and the order of the logged parameters has been reversed.

Meridian Enterprise Server can now be configured to automatically poll a Meridian360 tenancy for import packages, download and scan the packages for dependencies, and import the documents into a Meridian Enterprise vault. If matching project documents already exist in the vault, they are superseded by new revisions. Otherwise, they are imported as new project documents.

The connection settings (including optional proxy server settings) for exchanging packages between Meridian Enterprise and Meridian360 can be set in the Meridian Enterprise Server Administration Console. The interval in minutes to poll for incoming packages from Meridian360 can be configured as well as whether or not the packages are scanned for dependencies by a background task. Import profiles can be created that specify Meridian360 as the data source.

The performance of viewing large audit logs has been improved.

The performance of creating references from documents that already have thousands of references in a large vault has been improved.

When packages are sent by a publishing job to Meridian360, the recipient of the package is now notified by email.

A new server registry value CollectExisting has been added to disable the functionality added by MRE-2355 and described in Client improvements.

The Meridian Enterprise Industry Template (.met file) can now be selected during server installation.

As a consequence of the new HTML progress component described in Client improvements, when it is enabled, electronic signatures made in the Meridian Web Client are now only logged to the audit database if the Enable Web Access client components option is disabled (HTML component enabled) for that user.

Account locking when a user exceeds the maximum number of failed logon or electronic signature attempts has also changed. Instead of locking the user’s Windows account, only the user’s Meridian account is locked. New options have been added to the account properties in Meridian Enterprise Administrator and in Meridian Enterprise Server Administration Console to manually lock or unlock accounts.

See also Access denied opening documents in Remote mode.

The Print list folder option in Meridian Enterprise Server has been removed.